Adiyogi Books

Why this is on the portfolio

Adiyogi Books isn't a software project in the same sense as the others on this site. It's an independent publishing brand : I picked the titles, commissioned the artwork, set up the supply chain, and ran the launch. The technical layer (storefront, discount automation, newsletter, social sync) is the part that's relevant here, but the reason it's on the portfolio is more direct: it ships real physical product to real customers, and a Forward Deployed Engineer who has never run a P&L is missing a layer of context.

What the operation looks like

The hybrid direct-to-consumer storefront and global print-on-demand fulfillment pipeline functions as follows:

• Three titles published. Children's spiritual literature, with all three currently available through the direct storefront and Amazon.
• Amazon KDP distribution. Print-on-demand fulfilment for the international long tail.
• Direct storefront. adiyogibooks.com handles direct orders with margin retention, plus the customer relationship for the newsletter.
• Automated discount codes. Time-limited and segment-limited codes managed without manual intervention.
• Newsletter subscription. Buyer-list capture with a per-launch email cadence.
• Social platform sync. Cross-platform announcement pipeline so launches don't require manual posting to each network.

Featured Literature & Mindset Showcase

Adiyogi Books specializes in illustrated children’s stories that blend spiritual wisdom, scientific growth principles, and child psychology to foster emotional stability, patience, and a growth mindset:

What I learned that transfers to engineering

Running a commercial brand teaches you which engineering decisions actually matter to the business and which ones are vanity work. Specific things I've internalised from running Adiyogi Books that I'd bring to an FDE role:

• The first version of any customer-facing surface should be obviously incomplete and obviously usable. Polish that exceeds the maturity of the underlying product is a tax on iteration.
• Discount logic is harder than it looks. The first time a code gets stacked unexpectedly with another promotion, you understand why payment systems are conservative.
• Email is the highest-trust channel a brand owns. Treat the newsletter codepath like production infrastructure: idempotent, observable, recoverable.
• Fulfilment errors are the most expensive bug class : not because of the lost margin, but because of the customer trust impact. Every Amazon-KDP edge case I've debugged feels like a P1 ticket from my support days.

Honest framing

This is a small independent operation. Order volumes are modest. The storefront is built on managed e-commerce, not custom infrastructure. I'm including it on the portfolio because the discipline of shipping a product all the way to a customer's mailbox is the right kind of context for a Forward Deployed role : not because it represents large-scale software work.

Where to look

The storefront is at adiyogibooks.com. Titles are also searchable on Amazon. The newsletter is open to anyone : you'll see the launch cadence and the brand voice if you subscribe.